parked: fix(sqlite): Reduce expand materialization for SQLite #557
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When processing queries that have
ORDER BY
orHAVING
clauses. SQLite materializes the whole result before applying them. Which has to happen beforeLIMIT
andOFFSET
can be applied. Therefor moving theexpand
expression out of the native query prevents them from being materialized.When applying the same approach to
Postgres
there is no change in performance. Indicating thatPostgres
is able to identify what is required to be materialized and what can be materialized after reducing the result set.An impacted query was found in the
sflight
example application: